Skip to content

Potential fix for code scanning alert no. 67: Insecure TLS configuration - #4823

Draft
mykaul wants to merge 1 commit into
masterfrom
fix_secure_tls
Draft

Potential fix for code scanning alert no. 67: Insecure TLS configuration#4823
mykaul wants to merge 1 commit into
masterfrom
fix_secure_tls

Conversation

@mykaul

@mykaul mykaul commented May 4, 2026

Copy link
Copy Markdown
Contributor

Potential fix for https://github.com/scylladb/scylla-manager/security/code-scanning/67

General fix: enforce modern TLS defaults by allowing only TLS 1.2+ and removing insecure/legacy cipher suite options. For this file, the safest minimal change is to eliminate the TLSv10 enum option from parsing and from TLSConfig() so insecure config cannot be constructed at all.

Best single fix in pkg/config/tls.go:

  1. Remove TLSv10 constant from the enum.
  2. Remove case TLSv10 from UnmarshalText, so user input cannot select it.
  3. Remove case TLSv10 block from TLSConfig(), including all insecure suites (this addresses all three alert variants in one change).
  4. Keep TLSv12 and TLSv13 behavior unchanged.

No new imports, methods, or dependencies are required.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Deprecate TLS < 1.2, remove insecure ciphers.

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant